CI(1) Unix Programmer's Manual CI(1) NNNAAAMMMEEE ci - check in RCS revisions SSSYYYNNNOOOPPPSSSIIISSS ccciii [_o_p_t_i_o_n_s] _f_i_l_e ... DDDEEESSSCCCRRRIIIPPPTTTIIIOOONNN ccciii stores new revisions into RCS files. Each file name ending in ,,,vvv is taken to be an RCS file. All others are assumed to be working files containing new revisions. ccciii deposits the contents of each working file into the corresponding RCS file. If only a working file is given, ccciii tries to find the corresponding RCS file in an RCS subdirectory and then in the working file's directory. For more details, see FILE NAMING below. For ccciii to work, the caller's login must be on the access list, except if the access list is empty or the caller is the superuser or the owner of the file. To append a new revision to an existing branch, the tip revision on that branch must be locked by the caller. Otherwise, only a new branch can be created. This restriction is not enforced for the owner of the file if non-strict locking is used (see rrrcccsss(1)). A lock held by someone else may be broken with the rrrcccsss command. Normally, ccciii checks whether the revision to be deposited is different from the preceding one. If it is not different, ccciii aborts the deposit, asking beforehand if possible. A deposit can be forced with the ---fff option. For each revision deposited, ccciii prompts for a log message. The log message should summarize the change and must be terminated by end-of-file or by a line containing ...\ by itself. If several files are checked in ccciii asks whether to reuse the previous log message. If the standard input is not a terminal, ccciii suppresses the prompt and uses the same log message for all files. See also ---mmm. The number of the deposited revision can be given by any of the options ---fff, ---III, ---kkk, ---lll, ---qqq, ---rrr, or ---uuu. If the RCS file does not exist, ccciii creates it and deposits the contents of the working file as the initial revision (default number: 111...111). The access list is initialized to empty. Instead of the log message, ccciii requests descriptive text (see ---ttt below). OOOPPPTTTIIIOOONNNSSS ---rrr[rev]]] assigns the revision number _r_e_v to the checked-in revision, releases the corresponding lock, and deletes the working file. This is the default. _r_e_v may be symbolic, numeric, or mixed. If _r_e_v is a revision number, it must be higher than the latest one on the branch to which _r_e_v belongs, or must start a new branch. If _r_e_v is a branch rather than a revision number, the new revision is appended to that branch. The level number is obtained by incrementing the tip revision number of that branch. If _r_e_v indicates a non-existing \*(Dt 1 CI(1) Unix Programmer's Manual CI(1) branch, that branch is created with the initial revision numbered _r_e_v...111... If _r_e_v is omitted, ccciii tries to derive the new revision number from the caller's last lock. If the caller has locked the tip revision of a branch, the new revision is appended to that branch. The new revision number is obtained by incrementing the tip revision number. If the caller locked a non-tip revision, a new branch is started at that revision by incrementing the highest branch number at that revision. The default initial branch and level numbers are 111. If _r_e_v is omitted and the caller has no lock, but owns the file and locking is not set to _s_t_r_i_c_t, then the revision is appended to the default branch (normally the trunk; see the ---bbb option of rrrcccsss(1)). Exception: On the trunk, revisions can be appended to the end, but not inserted. ---fff[rev]]] forces a deposit; the new revision is deposited even it is not different from the preceding one. ---kkk[rev]]] searches the working file for keyword values to determine its revision number, creation date, state, and author (see cccooo(1)), and assigns these values to the deposited revision, rather than computing them locally. It also generates a default login message noting the login of the caller and the actual checkin date. This option is useful for software distribution. A revision that is sent to several sites should be checked in with the ---kkk option at these sites to preserve the original number, date, author, and state. The extracted keyword values and the default log message may be overridden with the options ---ddd, ---mmm, ---sss, ---www, and any option that carries a revision number. ---lll[rev]]] works like ---rrr, except it performs an additional cccooo\\\ ---lll for the deposited revision. Thus, the deposited revision is immediately checked out again and locked. This is useful for saving a revision although one wants to continue editing it after the checkin. ---uuu[rev]]] works like ---lll, except that the deposited revision is not locked. This lets one read the working file immediately after checkin. ---qqq[rev]]] quiet mode; diagnostic output is not printed. A revision that is not different from the preceding one is not deposited, unless ---fff is given. ---III[rev]]] interactive mode; the user is prompted and questioned even if the standard input is not a terminal. ---ddd[date]]] uses _d_a_t_e for the checkin date and time. The _d_a_t_e is specified in free format as explained in cccooo(1). This is useful for lying about \*(Dt 2 CI(1) Unix Programmer's Manual CI(1) the checkin date, and for ---kkk if no date is available. If _d_a_t_e is empty, the working file's time of last modification is used. ---mmm_m_s_g uses the string _m_s_g as the log message for all revisions checked in. ---nnn_n_a_m_e assigns the symbolic name _n_a_m_e to the number of the checked-in revision. ccciii prints an error message if _n_a_m_e is already assigned to another number. ---NNN_n_a_m_e same as ---nnn, except that it overrides a previous assignment of _n_a_m_e. ---sss_s_t_a_t_e sets the state of the checked-in revision to the identifier _s_t_a_t_e. The default state is EEExxxppp. ---ttt_f_i_l_e writes descriptive text from the contents of the named _f_i_l_e into the RCS file, deleting the existing text. The _f_i_l_e name may not begin with ---. ---ttt---_s_t_r_i_n_g Write descriptive text from the _s_t_r_i_n_g into the RCS file, deleting the existing text. The ---ttt option, in both its forms, has effect only during an initial checkin; it is silently ignored otherwise. During the initial checkin, if ---ttt is not given, ccciii obtains the text from standard input, terminated by end-of-file or by a line containing ...\ by itself. The user is prompted for the text if interaction is possible; see ---III. For backward compatibility with older versions of RCS, a bare ---ttt option is ignored. ---www_l_o_g_i_n uses _l_o_g_i_n for the author field of the deposited revision. Useful for lying about the author, and for ---kkk if no author is available. ---VVV_n Emulate RCS version _n. See cccooo(1) for details. FFFIIILLLEEE NNNAAAMMMIIINNNGGG Pairs of RCS files and working files may be specified in three ways (see also the example section of cccooo(1)). 1) Both the RCS file and the working file are given. The RCS file name is of the form _p_a_t_h_1///_w_o_r_k_f_i_l_e,,,vvv and the working file name is of the form _p_a_t_h_2///_w_o_r_k_f_i_l_e where _p_a_t_h_1/// and _p_a_t_h_2/// are (possibly different or empty) paths and _w_o_r_k_f_i_l_e is a file name. 2) Only the RCS file is given. Then the working file is created in the current directory and its name is derived from the name of the RCS file by removing _p_a_t_h_1/// and the suffix ,,,vvv. \*(Dt 3 CI(1) Unix Programmer's Manual CI(1) 3) Only the working file is given. Then ccciii looks for an RCS file of the form _p_a_t_h_2///RRRCCCSSS///_w_o_r_k_f_i_l_e,,,vvv or _p_a_t_h_2///_w_o_r_k_f_i_l_e,,,vvv (in this order). If the RCS file is specified without a path in 1) and 2), then ccciii looks for the RCS file first in the directory ...///RRRCCCSSS and then in the current directory. FFFIIILLLEEE MMMOOODDDEEESSS An RCS file created by ccciii inherits the read and execute permissions from the working file. If the RCS file exists already, ccciii preserves its read and execute permissions. ccciii always turns off all write permissions of RCS files. FFFIIILLLEEESSS Several temporary files may be created. A semaphore file is created in the directory containing the RCS file. The effective user+group must be able to read the RCS file and to search and write the directory containing the RCS file. Normally, the real user+group must be able to read the working file and to search and write the directory containing the working file; however, some older hosts that do not conform to Posix 1003.1-1990 cannot easily switch between real and effective ids, so on these hosts the effective user+group is used for all accesses. The effective user+group is the same as the real user+group unless your copy of RCS has setuid or setgid privileges. These privileges yield extra security if RCS files are protected so that only the effective user+group can write RCS directories. Further protection can be achieved by granting access only to the effective user+group. ccciii never changes an RCS or working file; instead, it unlinks the file and creates a new one. This strategy breaks hard links to such files, but does not affect symbolic links. DDDIIIAAAGGGNNNOOOSSSTTTIIICCCSSS For each revision, ccciii prints the RCS file, the working file, and the number of both the deposited and the preceding revision. The exit status is zero if and only if all operations were successful. IIIDDDEEENNNTTTIIIFFFIIICCCAAATTTIIIOOONNN Author: Walter F. Tichy. Revision Number: 5.4; Release Date: 1990/12/04. Copyright (c) 1982, 1988, 1989 by Walter F. Tichy. Copyright (c) 1990 by Paul Eggert. SSSEEEEEE AAALLLSSSOOO co(1), ident(1), rcs(1), rcsdiff(1), rcsintro(1), rcsmerge(1), rlog(1), rcsfile(5) Walter F. Tichy, RCS--A System for Version Control, _S_o_f_t_w_a_r_e--_P_r_a_c_t_i_c_e & _E_x_p_e_r_i_e_n_c_e 111555, 7 (July 1985), 637-654. \*(Dt 4